Accessibility content editing, control and management

ABSTRACT

Method, system and computer program product for accessibility content editing, control and management. Digital content container for receiving plurality of elements modifiable via an application programming interface exposed by content structure thereof, and being associated with accessibility output for presentation responsive to processing by an assistive tool, is obtained. Responsive to receiving input indicating user selection of an element, an accessibility content editing interface is provided for obtaining modified accessibility output. The application programming interface is employed to modify the element by injection thereto the modified accessibility output to cause, responsive to the element being processed by an assistive tool applied to the digital content container, presentation of the modified accessibility output in substitution of the accessibility output associated with the element. Modified accessibility output from plurality of users is transmitted to data storage for recordation and review, for accessibility output sharing and/or predictive modelling purposes.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/712,147 filed on Apr. 3, 2022. The contents of the above applicationare all incorporated by reference as if fully set forth herein in itsentirety.

FIELD AND BACKGROUND OF THE INVENTION

Some embodiments described in the present disclosure relate to userexperience design and, more specifically, but not exclusively, toaccessibility content editing, control and management.

With the advent of telecommunications networks and computing devicesproliferation and ubiquity, the volume and extent of digital contentconsumer base and correspondingly its diversity level are in constantgrowth, giving rise to various demands and sometimes even legalobligations for inclusion and catering to particular needs of as manydistinct user populations and/or usage profile types as possible.

One prominent example of such population of users attracting specialattention and treatment is that of persons with disabilities, such asfor example, visually- and/or motor-impaired individuals. The term“accessibility” often used in this context refers to the ability ofdisabled people to use a product or service as effectively as oneswithout a disability.

In the context of digital content, such as for example, contentdelivered over the worldwide web via communication channel(s) such asthe Internet and/or the like, assistive technologies and/oraccessibility arrangements for users with disabilities may be utilizedin order to render the content intelligible for such users.

One prevalent assistive technology or accessibility tool is a screenreader for use by visually impaired users, e.g., blind persons orindividuals with poor vision. Screen readers are assistive technologiesthat attempt to convey to a user what people with typical eyesight seeon a display, via non-visual means such as, for example, text-to-speech,sound icons, non-spoken audio feedback or a Braille device. Suchtechnologies may operate by applying a wide variety of techniques thatinclude, for example, interacting with dedicated accessibility APIs,using various operating system features (like inter-processcommunication and querying user interface properties), and employinghooks that intercept messages and/or events passed between softwarecomponents.

SUMMARY OF THE INVENTION

It is an object of the present disclosure to describe a system and amethod for accessibility content editing, control and management.

The foregoing and other objects are achieved by the features of theindependent claims. Further implementation forms are apparent from thedependent claims, the description and the figures.

According to one aspect of some embodiments of the disclosed subjectmatter there is provided a method for providing a user interface forediting accessibility content, comprising: obtaining a digital contentcontainer configured for receiving a plurality of elements, wherein anelement of the plurality of elements is associated with an accessibilityoutput for presentation to a user responsive to the element beingprocessed by an assistive tool applied to the digital content container,wherein the digital content container is associated with a contentstructure exposing an application programming interface enablingmodification of the element; responsive to receiving from the user aninput indicating selection of the element, providing the user with anaccessibility content editing user interface for obtaining from the usera modified accessibility output; and employing the applicationprogramming interface for modifying the element, by which the modifiedaccessibility output obtained from the user is injected to the elementto cause, responsive to the element being processed by an assistive toolapplied to the digital content container, presentation of the modifiedaccessibility output to the user in substitution of the accessibilityoutput associated with the element.

According to some embodiments of the disclosed subject matter, themethod further comprising reproducing, for presentation to the user, themodified accessibility output using the assistive tool.

According to some embodiments of the disclosed subject matter, themethod further comprising processing the element by the assistive toolprior to providing the user with the accessibility content editing userinterface, whereby the accessibility output is presented to the user.

According to some embodiments of the disclosed subject matter, themethod further comprising transmitting the modified accessibility outputto a data store.

According to some embodiments of the disclosed subject matter, themethod further comprising: responsive to obtaining the digital contentcontainer, retrieving from a data store for at least one element of theplurality of elements a stored modified accessibility output, andemploying the application programming interface for modifying the atleast one element, by which an accessibility output associated with arespective element of the at least one element is substituted by thestored modified accessibility output retrieved for the respectiveelement from the data store.

According to some embodiments of the disclosed subject matter, theplurality of elements being configured to be displayed on-screen forbeing visually perceived and the accessibility output is of a typeselected from the group consisting of: an audio output; and, a tacticaloutput.

According to some embodiments of the disclosed subject matter, theaccessibility content editing user interface is of a type selected fromthe group consisting of: a graphical user interface; a voice activateduser interface.

According to some embodiments of the disclosed subject matter, theaccessibility content editing user interface being configured to presentthe user at least one optional accessibility content modificationapplicable for the element.

According to another aspect of some embodiments of the disclosed subjectmatter there is provided a method for sharing accessibility contentamong a plurality of users, comprising: obtaining a digital contentcontainer configured for receiving a plurality of elements, wherein anelement of the plurality of elements is associated with an accessibilityoutput for presentation to a user responsive to the element beingprocessed by an assistive tool applied to the digital content container,wherein the digital content container is associated with a contentstructure exposing an application programming interface enablingmodification of the element; responsive to receiving from the user aninput indicating selection of the element, providing the user with anaccessibility content editing user interface for obtaining from the usera modified accessibility output, which modified accessibility output isindicated as a contributor content; transmitting the modifiedaccessibility output indicated as a contributor content to a data storeconfigured for allowing retrieval thereof for review by an administratorand recordation thereof responsive to approval by the administrator asstored modified accessibility output, wherein the data store isconfigured for returning thereof responsive to a request for retrievalof stored modified accessibility output for the digital contentcontainer, whereby enabling, responsive to the modified accessibilityoutput being received from the data store at a device of at least oneother user, employing the application programming interface formodifying the element, by which the modified accessibility outputobtained from the data store is injected to the element to cause,responsive to the element being processed by an assistive tool appliedto the digital content container, presentation of the modifiedaccessibility output to the at least one other user in substitution ofthe accessibility output associated with the element.

According to some embodiments of the disclosed subject matter the methodfurther comprising: responsive to obtaining the digital contentcontainer, retrieving from the data store for at least one element ofthe plurality of elements a stored modified accessibility output, andemploying the application programming interface for modifying the atleast one element, by which an accessibility output associated with arespective element of the at least one element is substituted by thestored modified accessibility output retrieved for the respectiveelement from the data store.

According to yet another aspect of some embodiments of the disclosedsubject matter there is provided a computer program product forproviding a user interface for editing accessibility content,comprising: a non-transitory computer readable storage medium; andprogram instructions for executing, by a processor, a method comprising:obtaining a digital content container configured for receiving aplurality of elements, wherein an element of the plurality of elementsis associated with an accessibility output for presentation to a userresponsive to the element being processed by an assistive tool appliedto the digital content container, wherein the digital content containeris associated with a content structure exposing an applicationprogramming interface enabling modification of the element; responsiveto receiving from the user an input indicating selection of the element,providing the user with an accessibility content editing user interfacefor obtaining from the user a modified accessibility output; andemploying the application programming interface for modifying theelement, by which the modified accessibility output obtained from theuser is injected to the element to cause, responsive to the elementbeing processed by an assistive tool applied to the digital contentcontainer, presentation of the modified accessibility output to the userin substitution of the accessibility output associated with the element.

According to yet another aspect of some embodiments of the disclosedsubject matter there is provided a computer program product for sharingaccessibility content among a plurality of users, comprising: anon-transitory computer readable storage medium; and programinstructions for executing, by a processor, a method comprising:obtaining a digital content container configured for receiving aplurality of elements, wherein an element of the plurality of elementsis associated with an accessibility output for presentation to a userresponsive to the element being processed by an assistive tool appliedto the digital content container, wherein the digital content containeris associated with a content structure exposing an applicationprogramming interface enabling modification of the element; responsiveto receiving from the user an input indicating selection of the element,providing the user with an accessibility content editing user interfacefor obtaining from the user a modified accessibility output, whichmodified accessibility output is indicated as a contributor content;transmitting the modified accessibility output indicated as acontributor content to a data store configured for allowing retrievalthereof for review by an administrator and recordation thereofresponsive to approval by the administrator as stored modifiedaccessibility output, wherein the data store is configured for returningthereof responsive to a request for retrieval of stored modifiedaccessibility output for the digital content container, wherebyenabling, responsive to the modified accessibility output being receivedfrom the data store at a device of at least one other user, employingthe application programming interface for modifying the element, bywhich the modified accessibility output obtained from the data store isinjected to the element to cause, responsive to the element beingprocessed by an assistive tool applied to the digital content container,presentation of the modified accessibility output to the at least oneother user in substitution of the accessibility output associated withthe element.

According to yet another aspect of some embodiments of the disclosedsubject matter there is provided a system for providing a user interfacefor editing accessibility content, comprising: a processing circuitryadapted to execute a code for performing a method comprising: obtaininga digital content container configured for receiving a plurality ofelements, wherein an element of the plurality of elements is associatedwith an accessibility output for presentation to a user responsive tothe element being processed by an assistive tool applied to the digitalcontent container, wherein the digital content container is associatedwith a content structure exposing an application programming interfaceenabling modification of the element; responsive to receiving from theuser an input indicating selection of the element, providing the userwith an accessibility content editing user interface for obtaining fromthe user a modified accessibility output; and employing the applicationprogramming interface for modifying the element, by which the modifiedaccessibility output obtained from the user is injected to the elementto cause, responsive to the element being processed by an assistive toolapplied to the digital content container, presentation of the modifiedaccessibility output to the user in substitution of the accessibilityoutput associated with the element.

According to yet another aspect of some embodiments of the disclosedsubject matter there is provided a system for sharing accessibilitycontent among a plurality of users, comprising: a processing circuitryadapted to execute a code for performing a method comprising: obtaininga digital content container configured for receiving a plurality ofelements, wherein an element of the plurality of elements is associatedwith an accessibility output for presentation to a user responsive tothe element being processed by an assistive tool applied to the digitalcontent container, wherein the digital content container is associatedwith a content structure exposing an application programming interfaceenabling modification of the element; responsive to receiving from theuser an input indicating selection of the element, providing the userwith an accessibility content editing user interface for obtaining fromthe user a modified accessibility output, which modified accessibilityoutput is indicated as a contributor content; transmitting the modifiedaccessibility output indicated as a contributor content to a data storeconfigured for allowing retrieval thereof for review by an administratorand recordation thereof responsive to approval by the administrator asstored modified accessibility output, wherein the data store isconfigured for returning thereof responsive to a request for retrievalof stored modified accessibility output for the digital contentcontainer, whereby enabling, responsive to the modified accessibilityoutput being received from the data store at a device of at least oneother user, employing the application programming interface formodifying the element, by which the modified accessibility outputobtained from the data store is injected to the element to cause,responsive to the element being processed by an assistive tool appliedto the digital content container, presentation of the modifiedaccessibility output to the at least one other user in substitution ofthe accessibility output associated with the element.

Other systems, methods, features, and advantages of the presentdisclosure will be or become apparent to one with skill in the art uponexamination of the following drawings and detailed description. It isintended that all such additional systems, methods, features, andadvantages be included within this description, be within the scope ofthe present disclosure, and be protected by the accompanying claims.

Unless otherwise defined, all technical and/or scientific terms usedherein have the same meaning as commonly understood by one of ordinaryskill in the art to which embodiments. Although methods and materialssimilar or equivalent to those described herein can be used in thepractice or testing of embodiments, exemplary methods and/or materialsare described below. In case of conflict, the patent specification,including definitions, will control. In addition, the materials,methods, and examples are illustrative only and are not intended to benecessarily limiting.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Some embodiments are herein described, by way of example only, withreference to the accompanying drawings. With specific reference now tothe drawings in detail, it is stressed that the particulars shown are byway of example and for purposes of illustrative discussion ofembodiments. In this regard, the description taken with the drawingsmakes apparent to those skilled in the art how embodiments may bepracticed.

In the drawings:

FIG. 1A is a schematic illustration of an exemplary website pagecontaining an interactive element;

FIG. 1B is a schematic illustration of an exemplary website pagecontaining an interactive element reviewed using an accessibilitycontent editor;

FIG. 1C is a schematic illustration of an exemplary website pagecontaining an interactive element edited using an accessibility contenteditor;

FIG. 2 is a sequence diagram of an optional flow of operations forproviding an accessibility content editing user interface;

FIG. 3 is a sequence diagram of an optional flow of operations foraccessibility content editing, control and management; and

FIG. 4 is a schematic illustration of an exemplary network environmentand architecture for accessibility content editing, control andmanagement.

DESCRIPTION OF SPECIFIC EMBODIMENTS OF THE INVENTION

Some embodiments described in the present disclosure relate to userexperience design and, more specifically, but not exclusively, toaccessibility content editing, control and management.

One technical challenge dealt with by the disclosed subject matter is tostreamline processes of accessibility content generation, enhancement,and/or dissemination by and among users developing, consuming,contributing to and/or otherwise interacting with an accessibility layerof a software product and/or service, such as for example, a website,web application program, and/or any likewise digital content source(s),as may be made available online.

Another technical challenge dealt with by the disclosed subject matteris to provide a user experience in a context of editing accessibilitycontent for blind and/or visually impaired users which is similar toand/or approximating that of WYSIWYG (What You See Is What You Get)editors as may be used for editing, reviewing, and/or otherwiseprocessing of visual content.

Digital content products and/or services such as websites, applicationsoftware, computing platforms, and/or the like, generally rely onpresentation of visually perceived content to their end-users. Blindand/or visually impaired users of digital content sources of this sortsuch as content streams originating from websites and/or the like mayrely, for example, on aural presentation of content via assistivetechnologies such as screen readers and/or the like. These technologiesmay rely on both semantic Hyper-Text Markup Language (HTML) markup andspecial markup such as Web Accessibility Initiative-Accessible RichInternet Applications (WAI-ARIA, or ARIA in short) labels in arespective accessibility layer. In general, an overwhelmingly largenumber of websites and likewise online digital content sources may beproviding poor and/or unsatisfactory aural experience to end-users.Blind users in particular may suffer regularly from a poor userexperience due to, inter alia, confusing screen reader feedback, poorlydesigned and/or unlabeled forms, poorly labeled images, lack ofcontextual information, lack of adequate attention to the auditoryexperience, and/or any likewise shortcomings and/or deficits, possiblyarising from one or more of multiple reasons and origins.

Designers, programmers, and testers of software products and/orservices, websites, and/or likewise digital content may generally focusoverwhelmingly on a visual state of the content. WYSIWYG editors maygreatly speed a process of iterative improvement, as a content authorand/or software designer may experience visually, nearly immediately,the visual design for flat screen, printed page, 3D display or otherrendering obtained as result, and can evaluate it visually quickly, at aglance. Programmers may see their requirements and expectations, andaccordingly may match it visually to the design. Testers likewise mayfind it easy to validate the results. Many stakeholders may thus beeasily involved, without any need for additional training or additionalrendering steps, bringing diverse opinions to bear. When a user makeschanges to the visual appearance of the content, e.g., changes the fontof a text and/or the like, the WYSIWYG editor in response makes theappropriate changes at the code level to enable the new and changedvisual appearance.

On the other hand, an accessibility layer such as an aural experiencemay not be so easy to design. Content authors may be required to authorcontent that is to be read by a screen reader, yet they may have noimmediate way to “hear” their content. Designers may be required tospecify content that is to be read by a screen reader, yet they may haveno immediate way to “hear” their designs. Programmers may need tomodulate settings on a variety of software control elements, such asHTML elements and attributes. Testers may need to validate that anexperience of consuming the digital content at hand, e.g., browsing andusing a website under test, by means of an assistive technology alone,is adequate. These tools may be complex and require training, sharplylimiting an ability of diverse stakeholders to experience in and bringtheir diverse opinions on the digital content to bear. WYSIWYG editorsfail to reduce the friction around the audio experience. Such editors donot reproduce the auditory experience, and do not offer control over theprogrammatic code that creates the auditory experience. Requiringassistive technologies to be installed at content authors', designers',programmers', developers' and testers' stations also does not reproducethe simple experience of WYSIWYG, as the technologies are complex,require training, and read the entire page as it becomes available viaaccessibility APIs or hooks, and thus are not optimized to read a singleelement on a page while it is being edited.

In some embodiments, a plurality of visual elements in a digital contentcontainer may be modelled as objects, that may be accessed and modifiedvia an Application Programming Interface (API), such as may be providedby a suitable content structure associated with the digital contentcontainer. A user interface configured for receiving from a user aninput of an edit to an accessibility content associated with an elementof the plurality of visual elements may be provided, optionally inresponse to selection of the element by the user. The element selectedmay be modified using the API so that the edit received as input fromthe user may be injected into the element in substitution of apre-existing element and/or its corresponding accessibility layerportion, thereby causing the edited accessibility content to bepresented to the user by an assistive tool applied to the digitalcontent container or a portion thereof. Optionally the user may be ableto experience such presentation of the edited accessibility content viathe assistive tool instantaneously and/or as soon as the content edit iscompleted and effected upon the element by modification thereof via theAPI as described herein.

In some embodiments, the edited accessibility content may be transferredto and recorded in a suitable data store, such as for example, asoftware development system, a code repository, a backend databaseserver, and/or the like. Optionally in response to a request foraccessing and/or loading the digital content container, the data storemay be queried for corresponding recorded edits stored therein and theedits may be retrieved therefrom and returned to an originator of therequest. The retrieved edits may then be injected into respectiveelements from the plurality of visual elements using the API so as toreplace former elements and/or their accessibility contents associatedtherewith and cause thereby to the respective modified accessibilitylayer be presented to the user in response to the digital contentcontainer and/or respective elements therein being processed by anassistive tool, in a same manner as may be done with an edit received asuser input, as described herein.

In some embodiments, edits to accessibility contents of one or moreelements of the plurality of visual elements in the digital contentcontainer may be proposed by one or more users. The proposed edits maybe received locally at a user device via the user interface as inputfrom a respective user of the one or more users and relayed to the datastore as user contributed suggested content. A special user withappropriate privileges, such as an administrator, a super-user, and/orthe like, may review the edits proposed by other users and accept orreject an edit proposal at discretion. Optionally accepted editproposals may be committed to the data store as binding and may beprovided on demand, such as in response to an access request to thedigital content container, so as to allow injection thereof intorespective elements using the API for modifying the respectiveaccessibility contents thereof accordingly, as described herein.

In some exemplary embodiments, snapshots and/or likewise documentationcapturing a state of the digital content container and/or of modifiedelements thereof immediately before and after an accessibility contentedit may be recorded in the data store and provided as a trainingdataset to a supervised machine learning (ML) algorithm and/orartificial intelligence (AI) model. The trained model may then beapplied to additional sources and/or documents containing digitalcontent for automatically generating predictions of accessibility layeredits in improvement of the user experience of consumers of the contentvia an assistive tool. The edit predictions from the model may bereviewed and approved or rejected by a human user in charge, similarlyas with suggestions from other human users, as described herein.Optionally the decisions of the user in adoption or discarding of asuggested edit by the model and/or another user may be used foradditional tuning and/or training of the model.

One technical effect of utilizing the disclosed subject matter is todefine an ability to design, program and evaluate an accessibility layerof a digital content such as an aural user experience and/or the like,with the immediacy and ease of the WYSIWYG experience. Stakeholders suchas content authors, designers, programmers, testers, and/or the like maybe able to aurally experience an entire web page, a part of a page or asingle interactive component on the page, optionally while usingstandard navigation interfaces (e.g., pointer, navigation keys, and/orthe like). When a change may be desired for a particular interactiveelement, an ability to make that change may be provided, such as forexample while a navigator may be positioned at that interactive element.The change may be recorded as needed in a respective softwaredevelopment system and code repository, similarly as described herein.Users can experience the change, as an aural experience for example, assoon as the change may be completed.

As a person skilled in the art may readily appreciate, the simplifiedand immediate access as provided by utilizing the disclosed subjectmatter may enable many diverse stakeholders to experience the page andchanges on the page as well, and their feedback can be fed back toprevious links on the supply chain, e.g., the content author, designerand/or the like. In effect, users utilizing the disclosed subject mattermay be provided with and take advantage of a What You Hear Is What YouGet (WYHIWYG) immediate and low friction editing and content creationexperience, regarding a text-to-speech audio assisted web pageexperience and/or any likewise accessible representation of the content,such as What You Feel Is What You Get (WYFIWYG) frictionless editingexperience focused on the accessible content that may be conveyed forexample by tactile interfaces (e.g., electronic Braille devices and/orthe like).

It will be appreciated that the disclosed subject matter may provide anability to create, read, update and/or delete software fields relatingto the accessibility layer in general and the heard experience inparticular, by supporting user reliance on audio for editing andvalidation of that editing.

It will further be appreciated that the disclosed subject matter maylend itself easily and conveniently to relying on crowd-sourcing forintroduction of audio fixes in whole or in part and additionally oralternatively may take advantage of sophisticated tools such as AI andML by training a model using supervised learning on a dataset of storedpre-fix and post-fix states.

An exemplary programming interface that may be utilized for carrying outsome embodiments of the disclosed subject matter is the API standardknown as Document Object Model (DOM), which is a cross-platform andlanguage-independent interface for accessing and manipulating ExtensibleMarkup Language (XML) and HTML documents, developed and maintained bythe World Wide Web Consortium (W3C) and Web Hypertext ApplicationTechnology Working Group (WHATWG) organizations. The DOM connects HTMLand/or XML documents such as, for example, web pages and/or the like toscripts and/or programming languages by representing the structure ofthe document in memory as a logical tree, wherein each branch of thetree ends in a node, and each node contains one or more objects. DOMmethods allow programmatic access to the tree, such that the document'sstructure, style, content, and/or the like can be changed dynamically.With the DOM, programmers can create and build documents, navigate theirstructure, and add, modify, or delete elements and content thereof.

For example, in case of a web page composed as an HTML document, anapplication program such as a web browser and/or the like that may beused to render the document, may employ for that purpose animplementation of DOM or a likewise internal model similar thereto. Whena web page is loaded, the web browser may create a DOM representation ofthe underlying HTML document which may act as an interface to thedocument and be harnessed by scripting languages such as JavaScript,Python, and/or the like for dynamic changing of the web page and/or itscontent, e.g., add, change, and remove any of the HTML elements andattributes, change any of the Cascading Style Sheets (CSS) style, reactto any and/or all of the existing events, create new events, and/or thelike.

For the sake of convenience and ease of understanding, the disclosedsubject matter in some embodiments thereof is described and illustratedherein with a focus on digital content of web pages and/or webapplication programs specifically, however it is not limited in suchmanner and may be utilized in any other likewise contexts of digitalcontent renditions, as can be readily apparent to a person skilled inthe art.

Similarly, while some embodiments of the disclosed subject matter aredescribed and illustrated herein out of convenience and for simplicitypurposes with reference to usage of screen readers as one commonassistive technology for making visual content accessible for low-visionand/or blind users, such depictions are not meant to be limiting inscope and any other appropriate assistive technologies and/or tools maybe employed as well, as a person skilled in the art would readilyappreciate.

Throughout the present disclosure, the terms “edit(s)”,“modification(s)”, “change(s)”, “remediation(s)”, “fix(es)”, and/or thelike may be used interchangeably to describe any alternates,enhancements, corrections, and/or the like made or to be made inconnection with contents of an accessibility layer associated withdigital content and/or any portion(s) thereof, and visual portion(s) inparticular.

Before explaining at least one embodiment in detail, it is to beunderstood that embodiments are not necessarily limited in itsapplication to the details of construction and the arrangement of thecomponents and/or methods set forth in the following description and/orillustrated in the drawings and/or the Examples. Implementationsdescribed herein are capable of other embodiments or of being practicedor carried out in various ways.

Embodiments may be a system, a method, and/or a computer programproduct. The computer program product may include a computer readablestorage medium (or media) having computer readable program instructionsthereon for causing a processor to carry out aspects of the embodiments.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, and any suitable combination of theforegoing. A computer readable storage medium, as used herein, is not tobe construed as being transitory signals per se, such as radio waves orother freely propagating electromagnetic waves, electromagnetic wavespropagating through a waveguide or other transmission media (e.g., lightpulses passing through a fiber-optic cable), or electrical signalstransmitted through a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofembodiments may be assembler instructions, instruction-set-architecture(ISA) instructions, machine instructions, machine dependentinstructions, microcode, firmware instructions, state-setting data, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++ or the like, and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The computer readable program instructions mayexecute entirely on the user's computer, partly on the user's computer,as a stand-alone software package, partly on the user's computer andpartly on a remote computer or entirely on the remote computer orserver. In the latter scenario, the remote computer may be connected tothe user's computer through any type of network, including a local areanetwork (LAN) or a wide area network (WAN), or the connection may bemade to an external computer (for example, through the Internet using anInternet Service Provider). In some embodiments, electronic circuitryincluding, for example, programmable logic circuitry, field-programmablegate arrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of embodiments.

Aspects of embodiments are described herein with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems), andcomputer program products according to embodiments. It will beunderstood that each block of the flowchart illustrations and/or blockdiagrams, and combinations of blocks in the flowchart illustrationsand/or block diagrams, can be implemented by computer readable programinstructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments. In this regard, each block in the flowchart or blockdiagrams may represent a module, segment, or portion of instructions,which comprises one or more executable instructions for implementing thespecified logical function(s). In some alternative implementations, thefunctions noted in the block may occur out of the order noted in thefigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustration, and combinations of blocks in the blockdiagrams and/or flowchart illustration, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts or carry out combinations of special purpose hardware and computerinstructions.

Reference is now made to FIG. 1A which is a schematic illustration of anexemplary website page containing an interactive element.

As shown in FIG. 1A, a website page such as 100 may be rendered on ascreen of a computing device, using for example a web browser such as102. The website page 100 may comprise an inaccessible interactiveelement such as 110, comprising text that reads “Click here to completeregistration” and a clickable link that encompasses a prefix portion ofthe text, i.e. “Click here”. The inaccessible interactive element 110may be rendered by an assistive technology (e.g., a screen reader) as“Click here, link”, thus without additional details, such as contextualand/or likewise information being made available the link may not besufficiently informative to a user relying on the assistive technology.

Reference is now made to FIG. 1B which is a schematic illustration of anexemplary website page containing an interactive element reviewed usingan accessibility content editor.

As shown in FIG. 1B, a user interface of an accessibility content editorsuch as 120 may be provided, for example by displaying thereof on thescreen of the computing device on which the web browser 102 is used fordisplaying the website page 100 containing the inaccessible interactiveelement 110. The user interface 120 may be displayed for example as anoverlay on top of the web browser 102 and/or website page 100, alongsidethereof, and/or the like. The accessibility content editor and userinterface 120 thereof may be used for reviewing and/or editing anauditory experience and/or the like of the website page 100. Optionallythe accessibility content editor may be a software widget, such as aweb, desktop, and/or mobile widget and/or the like that may be executedby a suitable widget engine such as for example a web browser and/or thelike.

The interactive element 110 may be selected by a user for examinationthereof, for example by pointing and clicking on the interactive element110 using a pointing device and/or the like. Optionally, descriptiveinformation such as 125 may be provided to assist the user editing theinteractive element 110, for example, as illustrated in FIG. 1B, thedescriptive information 125 may be displayed on-screen, e.g., proximallyto interactive element 110, and may read for example, “Sighted users seeClick here. Blind users hear click here, link.”

In response to selection thereof by the user, the interactive element110 under review may be retrieved and/or otherwise accessed by theaccessibility content editor and accordingly indicated as such in theuser interface 120. Optionally the user interface 120 may show theinteractive element 110 as one of a list of all interactive elements onthe page 100. In case user interface 120 is of an auditory experienceeditor, the user interface 120 may read the interactive element 110 tothe user, for example “Click here visited link.” Optionally the phrase“visited link” may be rendered by user interface 120 in another color,as it may be added by screen readers and/or likewise assistivetechnology due to the semantic link, even though these words may not bepresent in the content on the page 100. Optionally, the user interface120 may display the HTML, ARIA, XML, CSS, and/or any other likewiseprogrammatic settings that define the rendering of interactive element110.

Reference is now made to FIG. 1C which is a schematic illustration of anexemplary website page containing an interactive element edited using anaccessibility content editor.

The user may opt to change an accessibility content associated with theinteractive element 110, e.g., providing an alternate audio announcementfor presentation screen readers and/or likewise accessible experiencefor assistive tools, for example by clicking “edit” in the userinterface 120 while the interactive element 110 is under review,similarly as depicted herein with reference to FIG. 1B. In response, theaccessibility content editor and user interface 120 thereof may enteredit mode, and provide the user with an opened dialog box, a prompt,and/or the like for receiving input therefrom. The user may enter a fixinto the dialog box, such as for example “Click here to Register.”Optionally as illustrated in FIG. 1C, the user interface 120 maycomprise a semantic selector dropdown that may have an option “Button”selected, a “Hide from screen readers” button which may be off, a“Focusable element” button which may be on, and/or the like. Optionallythe user interface 120 may offer the ability to select the experiencebeing edited, whether it being an announcement by a screen reader,Braille rendering by a Braille device, and/or any other likewiseaccessible experience that may enabled by assistive technology andassociated programmatic markup languages.

The user may click “save” in the user interface 120 of the accessibilitycontent editor to save changes made to the interactive element 110 andintended for an assistive technology applied to an accessibility layerof the website page 100, such as a screen reader and/or the like, andoptionally thereby confirm that the interactive element 110 is nowaccessible for disabled users, such as for example visually impairedusers and/or users relying on assistive technology of the sort.

Reference is now made to FIG. 2 which is a sequence diagram of anoptional flow of operations for providing an accessibility contentediting user interface.

A user such as 201 may visit at 210 a website page such as 202. At 212,upon loading of the page 202 by a web content rendering program such asa web browser, a corresponding content structure, programmatic encodingand API such as a document object model (DOM) 203 may be initiated. At214, a user experience (UX) editor, such as UX widget 204, configuredfor allowing user 201 to review and/or edit an accessibility layer ofpage 202 may be initiated too. At 216, the UX widget 204 may issue arequest to get remediations for the accessibility layer of page 202 froma corresponding networked service of UX widget 204 such as UX backend205. At 218, the UX backend server 205 may return a set of fixes inresponse. At 220, the UX widget 204 may apply each received fix to theaccessibility layer of page 202 by modifying a respective element in thepage 202 using the API of the DOM 203.

At 222, the user 201 may select an element in the page 202, whichselection may be communicated to the UX widget 204. At 224, the UXwidget 204 may request an assistive technology such as reader 206 torender the element selected by the user 201 (in the case of a screenreader, the screen reader may announce the element). At 226, the reader206 may look up a text and/or likewise user experience for the selectedelement in the accessibility layer of page 202 by invoking the DOM 203for querying for an accessibility content of that element. At 228, acorresponding text may be returned in response, e.g., ‘shirt’ as in theillustrative example depicted in FIG. 2 . At 230, the reader 206 mayannounce the returned content to the user 201. The procedure carried outat 222 through 230 may be performed repeatedly for any number of times.

At 232, the user 201 may use the UX widget 204 to edit the accessibilitycontent of the element selected at 222, e.g., set the accessible textthereof to ‘red shirt’, as in the illustrative example depicted in FIG.2 . At 234, the UX widget 204 may modify the element using the API ofthe DOM 203, similarly as may be done at 220. At 236, the UX widget maytransfer to the UX backend 205 the edited accessibility content forstorage with pre-existing remediations such as returned at 218, using aput remediation command for example. The procedure carried out at 232through 236 may be optional and applied to any element and/orcombination of elements in the page 202, as well as to none thereof.

In some embodiments, modifying the element may entail locating allattributes, tags end values and/or identifying all markup fields thatmay be relevant to the accessibility layer and which contents thereofmay be required to be updated. The accessibility editor may have anextensible dictionary of program instructions that enable it to locatethe program instructions most related to the element selected forediting. Program instructions may take the form of attributes, tags,values and/or identifying markup fields written in HTML, XML, ResourceDescription Framework (RDF), CSS, JavaScript, and/or any likewise otherlanguages. Isolating the element's program instructions may be aprerequisite to deploying edits to the element.

In some embodiments, modifying the element may entail a capability ofdeploying new computer readable program instructions to cause the editedtext to be rendered by the assistive technology, e.g. announced by thescreen reader and/or the like. To deploy an edit, the accessibilityeditor may rely on one or more prediction models that predict how toedit the program instructions to implement the edited change. Adecision-making mechanism may accept multiple deployment predictions,then deploy the prediction with a highest confidence value. Oneexemplary prediction may rely on the context of the element's isolatedcode. A dictionary of markup changes based on context may be used, andeach context may be related to a predicted markup. For example, an imagemay have its screen reader announcement edited by modifying the ‘alt’attribute. A more complex prediction may rely on an AI model predictionbased on past behavior, for example. In some embodiments, there may beas many thousands of examples of people deploying edits. These edits mayserve as a supervised training model for an AI or ML system. The AI/MLsystem can then predict changes for previously unseen code examples.More complex predictions rely on visually interpreted code. Suchpredictive models may inspect the visual element and associate thisvisual appearance with deployed edits. These edits may serve as asupervised training model for an AI or ML system. The system can thenpredict changes for previously unseen code examples.

In some embodiments, decisions regarding the accessibility experiencemay be presented to the user for wizard-like deployment. For example, acheckbox may be presented where the user may check that an image ismerely decorative (meaning that it need not be announced by a screenreader).

Reference is now made to FIG. 3 which is a sequence diagram of anoptional flow of operations for accessibility content editing, controland management.

At 310, a contributor such as 300 may open a web page such as 302. At312, the contributor may select an element in the page 302. At 314, thecontributor 300 may input a proposed edit to an accessibility content ofthe element selected, e.g., set a text thereof to ‘red shirt’, using aclient program such as UX widget 304. At 316, the UX widget 304 maytransfer the contributed edit to a server such as UX backend 305.Similarly, at 318, another contributor such as 300 may open the page302. At 320, the other contributor may select the element, and at 322,use UX widget 304 to input a different proposed edit to the content,e.g., set the text to ‘blue shirt’. At 324, the UX widget 304 maytransfer the additional contributed edit to the UX backend 305 too.

At 326, an administrator such as 307 may access the UX backend 305 toget therefrom contributions of accessibility content edits as providedby one or more of the contributor(s) 300. At 328, the administrator 307may choose which of the contributions in the UX backend 305 to acceptand which to reject. At 330, the administrator 307 may put in the UXbackend 305 the remediations with each of which being flagged either asapproved or rejected, as applicable.

At 332, a user such as 308 may open the page 302. At 334, the UX widget304 may be initiated responsive to the page 302 loading. At 336, the UXwidget 304 may get approved remediations from the UX backend 305. At338, the remediations may be applied by the UX widget to the page 302,similarly as described herein.

Reference is now made to FIG. 4 which is a schematic illustration of anexemplary network environment and architecture for accessibility contentediting, control and management.

A plurality of users such as 401, 403, and 405, collectively denoted ascrowd 400, may use a software application container, such as for examplea web browser 413, configured for rendering content from a digitalcontent service such as a web application program (app) backend 420.Each of the users in the crowd 400 may consume the digital content,experience its user interface, and/or suggest fix(es) 410 to thatexperience in order to improve it, similarly as described herein.

An administrator or admin user such as 402 may have same capabilities asusers in the crowd 400. In addition, the admin user 402 may beauthorized to approve changes, or fix(es) 410 recommendations that mayaccordingly become committed and change as a result the digital contentfrom a pre-fixed version V1 to a fixed version V2. The administrator 402may interact with a web application via a web app page 414, and may alsoissue commands to a networked service controlling and managing anaccessible user experience of digital content such as UX backend 430.

The software application container such as the browser 413 may beconfigured to read digital content from the web app backend 420 andcommunicate it to an assistive technology, e.g. an audio processingengine, such as text-to-speech 416. Optionally the software applicationcontainer may be a mobile application, a bytecode application that mayrun on a dedicated processor, and/or any likewise instantiation of anapplication container, such as for example the browser 413 asillustrated in FIG. 4 . The application container 413 may also accessits own local application data storage (not shown). The applicationcontainer 413 may allow each of the users in the crowd 400 to experiencethe web app page 414 visually and/or aurally.

In some embodiments, a unit of auditory experience may be an interactiveelement such as for example a link, button, input field, textdescription, paragraph of text, and/or any combination of suchinteractive elements and/or the like. For example, the web app page 414shown in FIG. 4 may be a unit of auditory experience.

In some embodiments, an editor for reviewing and/or editingaccessibility content, such as the editor denoted in FIG. 4 asclick-and-edit 415, may be provided for example via the applicationcontainer 413. For a given unit of auditory experience, the editorclick-and-edit 415 editor may be configured to isolate the unit ofauditory experience, present an editing interface to a user such as theusers 401, 402, 403, and/or 405, and accept a user input to edit thatexperience. The edit may be applied in the application container 413,updating a respective code in the web app page 414, optionally withconcomitant changes to one or more other components comprised in and/orcoupled to the application container 413 as described herein, to createnew auditory experience. The fix(es) 410 may be packaged and transferredto the UX backend 430 and optionally to the web app backend 420 whereapplicable.

The application container 413 may comprise and/or be in communicationwith an assistive technology such as text to speech 416, configured tocreate for example an auditory experience and/or audio announcement ofcontent or structure on a user interface, software, web app, and/orlikewise digital content that may be found in the web app page 414.

Optionally the application container 413 may further comprise and/or bein communication with an assistive technology for auditory input ofcontent such as speech to text 417 which may be configured to detectspeech and translate that speech into symbols required by the web apppage 414, web app backend 420, and/or any likewise other softwarecomponents, as well as to record those symbols into fixes that, whenread by the text to speech 416 output assistive technology, mayre-create the input auditory experience.

Optionally the application container 413 may comprise and/or be incommunication with a translator interface such as 418 which may beconfigured to access in the UX backend 430 a corresponding translatorservice 460 for translating into other languages an output of the textto speech 416 assistive technology and/or an input of the speech to text417 assistive technology and/or of the click and edit 415 contenteditor.

Optionally the application container 413 may comprise and/or be incommunication with a suggestions interface such as 419 of acorresponding service such as AI suggestions 450 in the UX backend 430configured for making suggestions based on algorithmically generatedpredictions, related experiences, other fixes 410 suggested by otherusers as may be stored in storage 440, and/or the like as describedherein.

In some embodiments, fix(es) 410 may be any modified and/or alternateexperience such as a change request, change suggestion, alternateauditory experience, and/or the like. The fix(es) 410 may include forexample any information that may be sufficient to define whichinteractive elements may be required to be changed on the web app page414, a pre-existing code version prior to the change, an updated codeversion as may be obtained after the fix may be applied, and/or thelike.

The UX backend 430 may be a backend server system configured forcoordinating versions and changes to an accessibility layer of the webapp page 414, such as for example a networked available service fordelivering content, receiving fixes such as 410, making suggestions,and/or the like. Optionally UX backend 430 may further be configured forchanging the accessibility content from version V1 to V2 when receivingan appropriate authorization to do so, from admin user 402 for example.

In some embodiments a service such as AI predictions 450 may beconfigured to predict version changes based for example on itsrespective model 452 and training set 454. The AI predictions 450service may store changes made in the past, thereby forming a supervisedlearning training dataset, and generate AI or ML model(s) based on suchtraining sets. Optionally these generated model(s) 452 may be applied tonew and/or previously unseen interactive elements and thereby generatepredicted fixes for approval by users such as admin user 402 and/or thelike.

A translation service such as translator 460 may be configured toservice a translator interface such as 418 and/or other services in UXbackend 430. Translator 460 may be utilized to translate content fromone or more languages to one or more other languages, so that audiocontent in language L1 may be presented for example in language L2, L3,etc.

A storage service such as 440 may be employed to store for example webcontent, fixes, user identities and authorizations, and/or otherwisepersist any data needed by one or more software components of the UXbackend 430 server and/or click and edit 415 editor.

The UX backend 430 may comprise an application programming interface andbackend such as API 435 to enable communication between the one or moresoftware components of the UX backend 430 and/or of the click and edit415 editor. The API 435 may host and supply a software application whichmay deliver the user experience that may be subject to being fixed, suchas the click and edit 415 editor for example.

For illustration purposes, an exemplary scenario detailing a manner inwhich the disclosed subject matter may be used in practice is describedherein. In this exemplary scenario, web content may be available in aversion “V1”, with interactive elements “IE1”, “IE2”, etc., that mayfeature semantic content and/or markup specifically for an accessibilitylayer (e.g., WAI ARIA tags). Version “V1” may be made ready for accessin a browser and by assistive technology, for example. A primary user ordesigner “U1” may experience “V1” via a screen reader or assistivetechnology. One announcement on “IE1” may seem to “U1” to need fixing tooffer an improved user experience. “U1” may operate a ‘hit to edit’interface of an accessibility content editor such as disclosed herein.The editor may mark the relevant code (semantic, WAI ARIA or otherwise)as being edited and open the edit user interface for “U1” to input theirfix. “U1” may input a fix by any input provision means supported by theedit user interface (e.g., speaking it, typing it, uploading it, and/orthe like). The fix may be applied to the relevant code that affects“IE1”. “U1” may hit ‘continue’ and “U1” now experience a version “V2”that includes the fix. Version “V2” may also be shared with other users“U2”, “U3” etc. who may offer fixes as well that can be reviewed by“U1”.

It will be appreciated by a person skilled in the art that the disclosedsubject matter is advantageous over other methods and systems available,by providing a vastly increased efficiency in improving the heardexperience and/or likewise accessibility layer. Under pre-existingapproaches, the programmatic elements that modify and inform operationand/or behavior of a screen reader and/or likewise assistive technologymay be located in disparate locations, as singular attributes that mightbe buried in nonintuitive places in the code and/or document contentstructure, e.g. in the DOM tree and/or the like. By utilizing thedisclosed subject matter all attributes, tags and values relevant to theaccessibility layer may be located and a user may be allowed to editthem as if they are located in one virtual space. Greater simplicity inauditing, editing and improving the heard experience for example maythus be achieved, by an ability of the disclosed subject matter toidentify the markup fields that generate the heard experience, as wellas providing users with an ability to hear that experience immediatelyupon editing thereof.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments disclosed. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the described embodiments. The terminologyused herein was chosen to best explain the principles of theembodiments, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

It is expected that during the life of a patent maturing from thisapplication many relevant accessibility content editing, control andmanagement systems and methods will be developed and the scope of theterm accessibility content editors is intended to include all such newtechnologies a priori.

As used herein the term “about” refers to ±10%.

The terms “comprises”, “comprising”, “includes”, “including”, “having”and their conjugates mean “including but not limited to”. This termencompasses the terms “consisting of” and “consisting essentially of”.

The phrase “consisting essentially of” means that the composition ormethod may include additional ingredients and/or steps, but only if theadditional ingredients and/or steps do not materially alter the basicand novel characteristics of the claimed composition or method.

As used herein, the singular form “a”, “an” and “the” include pluralreferences unless the context clearly dictates otherwise. For example,the term “a compound” or “at least one compound” may include a pluralityof compounds, including mixtures thereof.

The word “exemplary” is used herein to mean “serving as an example,instance or illustration”. Any embodiment described as “exemplary” isnot necessarily to be construed as preferred or advantageous over otherembodiments and/or to exclude the incorporation of features from otherembodiments.

The word “optionally” is used herein to mean “is provided in someembodiments and not provided in other embodiments”. Any particularembodiment may include a plurality of “optional” features unless suchfeatures conflict.

Throughout this application, various embodiments may be presented in arange format. It should be understood that the description in rangeformat is merely for convenience and brevity and should not be construedas an inflexible limitation on the scope of embodiments. Accordingly,the description of a range should be considered to have specificallydisclosed all the possible subranges as well as individual numericalvalues within that range. For example, description of a range such asfrom 1 to 6 should be considered to have specifically disclosedsubranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4,from 2 to 6, from 3 to 6 etc., as well as individual numbers within thatrange, for example, 1, 2, 3, 4, 5, and 6. This applies regardless of thebreadth of the range.

Whenever a numerical range is indicated herein, it is meant to includeany cited numeral (fractional or integral) within the indicated range.The phrases “ranging/ranges between” a first indicate number and asecond indicate number and “ranging/ranges from” a first indicate number“to” a second indicate number are used herein interchangeably and aremeant to include the first and second indicated numbers and all thefractional and integral numerals therebetween.

It is appreciated that certain features of embodiments, which are, forclarity, described in the context of separate embodiments, may also beprovided in combination in a single embodiment. Conversely, variousfeatures of embodiments, which are, for brevity, described in thecontext of a single embodiment, may also be provided separately or inany suitable subcombination or as suitable in any other describedembodiment. Certain features described in the context of variousembodiments are not to be considered essential features of thoseembodiments, unless the embodiment is inoperative without thoseelements.

Although embodiments have been described in conjunction with specificembodiments thereof, it is evident that many alternatives, modificationsand variations will be apparent to those skilled in the art.Accordingly, it is intended to embrace all such alternatives,modifications and variations that fall within the spirit and broad scopeof the appended claims.

It is the intent of the applicant(s) that all publications, patents andpatent applications referred to in this specification are to beincorporated in their entirety by reference into the specification, asif each individual publication, patent or patent application wasspecifically and individually noted when referenced that it is to beincorporated herein by reference. In addition, citation oridentification of any reference in this application shall not beconstrued as an admission that such reference is available as prior artto the present invention. To the extent that section headings are used,they should not be construed as necessarily limiting. In addition, anypriority document(s) of this application is/are hereby incorporatedherein by reference in its/their entirety.

What is claimed is:
 1. A method for providing a user interface forediting accessibility content, comprising: obtaining a content structureassociated with a digital content container configured for receiving aplurality of elements, wherein an element of the plurality of elementsis associated with an accessibility output providing for presentation toa user of an accessible representation of the element via at least onedifferently perceived medium responsive to the element being processedby an assistive tool applied to the digital content container andconfigured for transforming digital content user experience into the atleast one differently perceived medium, wherein the content structureexposing an application programming interface enabling modification ofthe element; responsive to receiving from the user an input indicatingselection of the element, providing the user with an accessibilitycontent editing user interface for obtaining from the user a modifiedaccessibility output providing for modifying the accessiblerepresentation of the element via the at least one differently perceivedmedium; and employing the application programming interface formodifying the element, by which the modified accessibility outputobtained from the user is injected to the element to cause, responsiveto the element being processed by the assistive tool, presentation tothe user of the accessible representation of the element provided by themodified accessibility output in substitution of the accessiblerepresentation provided by the accessibility output associated with theelement.
 2. The method of claim 1, further comprising reproducing, forpresentation to the user, the accessible representation provided by themodified accessibility output using the assistive tool.
 3. The method ofclaim 1, further comprising processing the element by the assistive toolprior to providing the user with the accessibility content editing userinterface, whereby the accessible representation provided by theaccessibility output is presented to the user.
 4. The method of claim 1,further comprising transmitting the modified accessibility output to adata store.
 5. The method of claim 1, further comprising: responsive toobtaining the digital content container, retrieving from a data storefor at least one element of the plurality of elements a stored modifiedaccessibility output, and employing the application programminginterface for modifying the at least one element, by which anaccessibility output associated with a respective element of the atleast one element is substituted by the stored modified accessibilityoutput retrieved for the respective element from the data store.
 6. Themethod of claim 1, wherein the plurality of elements being configured tobe displayed on-screen for being visually perceived and the accessiblerepresentation provided by the accessibility output is of a typeselected from the group consisting of: an audio output; and, a tacticaloutput.
 7. The method of claim 1, wherein the accessibility contentediting user interface is of a type selected from the group consistingof: a graphical user interface; a voice activated user interface.
 8. Themethod of claim 1, wherein the accessibility content editing userinterface being configured to present the user at least one optionalaccessibility content modification applicable for the element.
 9. Amethod for sharing accessibility content among a plurality of users,comprising: obtaining a content structure associated with a digitalcontent container configured for receiving a plurality of elements,wherein an element of the plurality of elements is associated with anaccessibility output providing for presentation to a user of anaccessible representation of the element via at least one differentlyperceived medium responsive to the element being processed by anassistive tool applied to the digital content container and configuredfor transforming digital content user experience into the at least onedifferently perceived medium, wherein the content structure exposing anapplication programming interface enabling modification of the element;responsive to receiving from the user an input indicating selection ofthe element, providing the user with an accessibility content editinguser interface for obtaining from the user a modified accessibilityoutput providing for modifying the accessible representation of theelement via the at least one differently perceived medium, whichmodified accessibility output is indicated as a contributor content;transmitting the modified accessibility output indicated as acontributor content to a data store configured for allowing retrievalthereof for review by an administrator and recordation thereofresponsive to approval by the administrator as stored modifiedaccessibility output, wherein the data store is configured for returningthereof responsive to a request for retrieval of stored modifiedaccessibility output for the digital content container, wherebyenabling, responsive to the modified accessibility output being receivedfrom the data store at a device of at least one other user, employingthe application programming interface for modifying the element, bywhich the modified accessibility output obtained from the data store isinjected to the element to cause, responsive to the element beingprocessed by the assistive tool, presentation to the at least one otheruser of the accessible representation of the element provided by themodified accessibility output in substitution of the accessiblerepresentation provided by the accessibility output associated with theelement.
 10. The method of claim 9, further comprising: responsive toobtaining the digital content container, retrieving from the data storefor at least one element of the plurality of elements a stored modifiedaccessibility output, and employing the application programminginterface for modifying the at least one element, by which anaccessibility output associated with a respective element of the atleast one element is substituted by the stored modified accessibilityoutput retrieved for the respective element from the data store.
 11. Acomputer program product for providing a user interface for editingaccessibility content, comprising: a non-transitory computer readablestorage medium; program instructions for executing, by a processor, themethod of claim
 1. 12. A computer program product for sharingaccessibility content among a plurality of users, comprising: anon-transitory computer readable storage medium; program instructionsfor executing, by a processor, the method of claim
 9. 13. A system forproviding a user interface for editing accessibility content,comprising: a processing circuitry adapted to execute a code forperforming the method of claim
 1. 14. A system for sharing accessibilitycontent among a plurality of users, comprising: a processing circuitryadapted to execute a code for performing the method of claim
 9. 15. Themethod of claim 9, further comprising reproducing, for presentation tothe user, the accessible representation provided by the modifiedaccessibility output using the assistive tool.
 16. The method of claim9, further comprising processing the element by the assistive tool priorto providing the user with the accessibility content editing userinterface, whereby the accessible representation provided by theaccessibility output is presented to the user.
 17. The method of claim9, wherein the plurality of elements being configured to be displayedon-screen for being visually perceived and the accessible representationprovided by the accessibility output is of a type selected from thegroup consisting of: an audio output; and, a tactical output.
 18. Themethod of claim 9, wherein the accessibility content editing userinterface is of a type selected from the group consisting of: agraphical user interface; a voice activated user interface.
 19. Themethod of claim 9, wherein the accessibility content editing userinterface being configured to present the user at least one optionalaccessibility content modification applicable for the element.